Dynamisys

FastEndpoints returns BadRequest on a Get

RichardHowells — Thu, 19 Jun 2025 16:06:00 GMT

I spent a fruitless evening trying to track down why my get request returned the badrequest result.Using FastEndpoints under net 9.Discovered that a get, with the content-type header application/json, seems to cause this problem. I conjecture that it's because gets normally have no body. I suspect the FastEndpoints code tries to deserialize an empty body as JSON. This results in a JSON parsing error; returned to the client as a bad request.Removing the content type header fixed the problem for me.

Octopus Deploy and .Net core. ASPNETCORE_ENVIRONMENT setting

RichardHowells — Thu, 09 Apr 2020 15:53:00 GMT

When an ASP.Net core application runs it inspects the ASPNETCORE_ENVIRONMENT environment variable to determine if it is running in development mode or production (or other) modes. This can be set from a variety of places. In .Net core 3 (maybe other versions) it can be set from the web config file... But that value in the web config is also meddled with when you hit F5 in Visual Studio, where it gets overwritten by a value in launchsettings.json (only used by visual studio - not required on the live server). Octopus deploy would be very happy if it said... ...Octopus is excellent at finding those variables and subbing values in there. This does not work because every time you hit F5 the octopus variable gets overwritten with a value from launchsettings So I added a custom deployment step to my Octopus Deploy based on Benjamin Tam's script https://library.octopus.com/step-templates/c7f96ab8-a0d3-4f01-928e-c8cb78ab108c/ I puzzled for AGES over finding out the directory that the .Net Core app was deployed, by a previous step, so that I could reference the web config file. This worked for me... #{Octopus.Action[ASP.Net Core Website].Output.Package.InstallationDirectoryPath}\web.config Where "ASP.Net Core Website" is the actual name of the step deploying the .Net core website, as displayed in the Octopus UI. I may not have made the perfect choice of Octopus internal variable, but it works for my simple requirements. I also had to patch the script. For me; the path in the web.config xml down to the environment variable section had to be corrected. Original: $aspNetCore = $xml.configuration.location.'system.webServer'.aspNetCore Modified by me: $aspNetCore = $xml.configuration.'system.webServer'.aspNetCore

ASP.Net Core Identity - Invalid token on password reset

RichardHowells — Thu, 09 Apr 2020 15:37:00 GMT

I had Scaffolded some of the Identity code - so that I could send out emails for password resets. The sent out reset tokens did not work. I always saw the message 'Invalid token'. I'm not sure how I got to this state... How I fixed it I scaffolded the Account/ResetPassword as well. It worked for me to just run Add | Scaffolded Item | Identity and choose Account/ResetPassword. In the code for that I discovered (around line 60) that it was Base64 decoding the incoming token. My emailed out token didn't Base64 encode it. I removed the Base64 decoding from the scaffolded code. The emailed out tokens began working. Environment : ASP.Net Core 3, but the project was upgraded from version 2. I'm pretty sure that the emailed out password tokens used to work and I don't know at what point they stopped.